Skip to content

Conversation

@NicolasHug
Copy link
Member

@NicolasHug NicolasHug commented Dec 12, 2024

CP of #8671

I created the release/0.21 a few minutes before I landed #8671 on main, so this needs to be cherry-picked. This is by design: I need to closely monitor any potential issue with that specific PR, that's why I didn't land it on main before the branch cut. So, this is definitely not a "last minute rushed cherry-pick", it's 100% supposed to be part of this release, and having it as a CP helps debugging any potential problem.

@pytorch-bot
Copy link

pytorch-bot bot commented Dec 12, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/vision/8800

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit 422d919 with merge base a9a726a (image):

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@NicolasHug
Copy link
Member Author

I triggered 422d919 yesterday and everything is green (apart from unrelated windows GPU issue which is long-standing and unrelated).

@NicolasHug NicolasHug merged commit eafc293 into pytorch:release/0.21 Jan 10, 2025
65 of 66 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants